PutObject

Description

PutObject is used to upload files (Object).

Request Method

POST

Request Path

/apsara/route/OneRouter/PutObject

Request Parameters Common Parameters

Name	Location	Type	Required	Sample value	Description
x-oss-tagging	BODY	string	No	xx=1	specifies the label of the object. multiple labels can be set at the same time, for example: TagA = A & amp;TagB = B. indicates that Key and Value require advanced URL encoding. if an item does not have "=", Value is regarded as an empty character.
x-oss-object-acl	BODY	string	No	private	Specify the access permission when OSS creates an object. legal values: public-read, private, public-read-write
Cache-Control	BODY	string	No	no-cache	specifies the caching behavior of the web page when the object is downloaded. For more information, please refer to RFC2616.
x-oss-server-side-data-encryption	BODY	string	No	SM4	specifies the encryption algorithm of the object. If this option is not specified, Object uses the AES256 encryption algorithm. This option is only available if x-oss-server-side-encryption is valid for KMS. Value: SM4
regionId	BODY	string	Yes	No sample value for this parameter.	region id
Content-Disposition	BODY	string	No	attachment;filename=oss_download.jpg	specifies the name of the object when it is downloaded. For more information, please refer to RFC2616.
Content-Encoding	BODY	string	No	utf-8	specifies the content encoding format when the object is downloaded. For more information, please refer to RFC2616. type: string default value: none
Expires	BODY	string	No	Fri, 28 Feb 2012 05:38:42 GMT	expiration time. For more information, please refer to RFC2616. indicates that OSS will not restrict or verify this value.
x-oss-server-side-encryption	BODY	string	No	KMS	When creating an Object, specify the server-side encryption method. Value: AES256, KMS or SM4 after specifying this parameter, this parameter is returned in the response header. OSS encrypts and stores the uploaded object. When the object is downloaded, the response header will contain the x-oss-server-side-encryption, and the value will be set to the encryption algorithm of the object.
version	BODY	string	No	2016-01-01	version of api
x-oss-server-side-encryption-key-id	BODY	string	No	3dea0cae-5fd6-4bf8-8574-87c557******	KMS hosted user master key. This parameter is only available in x-oss-server-side-encryption is valid for KMS.
Content-MD5	BODY	string	No	uk8Os/oShU2MMhcajpeAVA==	calculates the MD5 value for the message content (excluding the header) according to the protocol RFC 1864 to obtain a 128-bit number, and base64 encodes the number as the Content-MD5 value of a message. The request header can be used to check the legality of the message (whether the message content is consistent with the time of sending). Although the request header is optional, OSS recommends that you use the request header for end-to-end checking.

Return data

Name	Type	Sample value	Description
RequestID	string	1E3D5A1E0-67CA-43DA-24BC-EAF2D5A1E4DC	Request id

Example

Successful Response example

{
 "RequestID":"1E3D5A1E0-67CA-43DA-24BC-EAF2D5A1E4DC"
}

Failed Response example

{
 "errorSample":
 {
  "resultCode":-1,
  "resultMsg":"system error",
  "result":null
 }

}